Add support for UART to the NET chip#145
Merged
bifurcation merged 10 commits intomainfrom Sep 12, 2025
Merged
Conversation
Collaborator
Author
|
It turns out we don't really need the async in the transmit direction. If the blocking transmit turns out to be an issue, we can investigate async later. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #140
To validate performance, I added a
PingandPongpacket types to the NET firmware, and logic to automatically respond to aPingwith aPong. It works reliably with the modified NET firmware flashed, though it's a bit finicky as to when in the lifecycle of the NET run you send thePing. I haven't gotten deep enough in the NET firmware to understand what's going on, but it's reliable enough that it seems like the basic UART logic works.There is a non-trivial conceptual shift here, in that
App::handleis nowasync. This works fine in theui-stm32crate, but is causing some trouble in theui-tauricrate (problems with holding locks on global state acrossawaitboundaries). As a result, the UART functionality is not currently implemented inui-tauri.